Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 52d0c00877c6f2acd27b79101f4b265075792be945ddf3008735691bd61276ea

Tx prefix hash: 1a3ae7c94dbd7e6458e62d6e7ad3c60cc4db67e612b11894a84195c2ca1f7d64
Tx public key: 79768eb9272849958984e399afda3c8a0ebcc29c893a6daade8a875abc0c90ed
Timestamp: 1701512149 Timestamp [UCT]: 2023-12-02 10:15:49 Age [y:d:h:m:s]: 02:063:05:29:22
Block: 904277 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 564871 RingCT/type: yes/0
Extra: 0179768eb9272849958984e399afda3c8a0ebcc29c893a6daade8a875abc0c90ed02110000000375e3f0e9000000000000000000

1 output(s) for total of 0.619091574000 dcy

stealth address amount amount idx
00: e62c3f9a653c0657783529f58ee711b2e477202c2d7813a5cba837f4a20fa8da 0.619091574000 1360998 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": 904287, "vin": [ { "gen": { "height": 904277 } } ], "vout": [ { "amount": 619091574, "target": { "key": "e62c3f9a653c0657783529f58ee711b2e477202c2d7813a5cba837f4a20fa8da" } } ], "extra": [ 1, 121, 118, 142, 185, 39, 40, 73, 149, 137, 132, 227, 153, 175, 218, 60, 138, 14, 188, 194, 156, 137, 58, 109, 170, 222, 138, 135, 90, 188, 12, 144, 237, 2, 17, 0, 0, 0, 3, 117, 227, 240, 233, 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