Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: db402b7fbde4e02421e64ca5cd1d630f7ce593bd385b094f1f6d31420e941c36

Tx prefix hash: e791eb4ef5c79f5a2c5bd82cbe2a98e6cfc4a308f313e19b1217faf63e29042f
Tx public key: 7676777191ac9e8bd11bdccf357f5e9d89af6e8fe3f87d548a90763fa411a470
Timestamp: 1645663318 Timestamp [UCT]: 2022-02-24 00:41:58 Age [y:d:h:m:s]: 02:303:05:29:11
Block: 445140 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 736138 RingCT/type: yes/0
Extra: 017676777191ac9e8bd11bdccf357f5e9d89af6e8fe3f87d548a90763fa411a4700211000000035eb576c5000000000000000000

1 output(s) for total of 20.562062718000 dcy

stealth address amount amount idx
00: 2d6d45d13f4ca6d381bb89dc0a116022155087070dc1aacc77e6bfbd3fdaaae0 20.562062718000 858649 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": 445150, "vin": [ { "gen": { "height": 445140 } } ], "vout": [ { "amount": 20562062718, "target": { "key": "2d6d45d13f4ca6d381bb89dc0a116022155087070dc1aacc77e6bfbd3fdaaae0" } } ], "extra": [ 1, 118, 118, 119, 113, 145, 172, 158, 139, 209, 27, 220, 207, 53, 127, 94, 157, 137, 175, 110, 143, 227, 248, 125, 84, 138, 144, 118, 63, 164, 17, 164, 112, 2, 17, 0, 0, 0, 3, 94, 181, 118, 197, 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