Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: 2e31493f3016942b09fede633011b0dbb1fa3e859088983f25451cb2f8934821

Tx prefix hash: dc880451a0ba10d0c6941baa6ca2aa277d59e397d753ea591f9618c6c8693cfc
Tx public key: d30b65a49960798d60687c72c74c05ec16625df8223d40bb86dcbabeef2edfe4
Timestamp: 1581365477 Timestamp [UCT]: 2020-02-10 20:11:17 Age [y:d:h:m:s]: 05:268:06:48:38
Block: 62277 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1342223 RingCT/type: yes/0
Extra: 01d30b65a49960798d60687c72c74c05ec16625df8223d40bb86dcbabeef2edfe40211000000ba724f989b000000000000000000

1 output(s) for total of 381.652662743000 dcy

stealth address amount amount idx
00: 8f9a7c4bcc6d4f81d690e42f746d3322e6affcde255f9773aa10fe96140877f9 381.652662743000 114846 of 0

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 62287, "vin": [ { "gen": { "height": 62277 } } ], "vout": [ { "amount": 381652662743, "target": { "key": "8f9a7c4bcc6d4f81d690e42f746d3322e6affcde255f9773aa10fe96140877f9" } } ], "extra": [ 1, 211, 11, 101, 164, 153, 96, 121, 141, 96, 104, 124, 114, 199, 76, 5, 236, 22, 98, 93, 248, 34, 61, 64, 187, 134, 220, 186, 190, 239, 46, 223, 228, 2, 17, 0, 0, 0, 186, 114, 79, 152, 155, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8