Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 652a8fcb00b60e6ef9a652f9f4e8362ba426deb52e3dffc21681e62ccbf41d08

Tx prefix hash: c3b4c7f5d0bfad8733db636319cc6f6ab807f4aa96f501a5cb01964d432bcf0b
Tx public key: ca2ef33a1b8a4c27d8242f281d69d8383f6b232369182fddb77990356ecd63a6
Timestamp: 1650345532 Timestamp [UCT]: 2022-04-19 05:18:52 Age [y:d:h:m:s]: 02:330:04:18:46
Block: 483339 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 755697 RingCT/type: yes/0
Extra: 01ca2ef33a1b8a4c27d8242f281d69d8383f6b232369182fddb77990356ecd63a6021100000007cb8520c2000000000000000000

1 output(s) for total of 15.363758762000 dcy

stealth address amount amount idx
00: 0f73c7ffdfecd4816442d9d56301fe981dde171d6d06da4a2f4a3dd4014d73e9 15.363758762000 904998 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": 483349, "vin": [ { "gen": { "height": 483339 } } ], "vout": [ { "amount": 15363758762, "target": { "key": "0f73c7ffdfecd4816442d9d56301fe981dde171d6d06da4a2f4a3dd4014d73e9" } } ], "extra": [ 1, 202, 46, 243, 58, 27, 138, 76, 39, 216, 36, 47, 40, 29, 105, 216, 56, 63, 107, 35, 35, 105, 24, 47, 221, 183, 121, 144, 53, 110, 205, 99, 166, 2, 17, 0, 0, 0, 7, 203, 133, 32, 194, 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