Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 232feb730066e2ced26bb9a69b6edd8e5d6e59513697b744cc02726344b26575

Tx prefix hash: 3e7cca2997bbeaf3c02ee49a8d4f2443b50ba2392a54eea97477485c741fb9e3
Tx public key: d2bb8c889f31da0e7a3a855e9b63ce8af9c5499205e5905dd5d938557f987ed5
Timestamp: 1665205995 Timestamp [UCT]: 2022-10-08 05:13:15 Age [y:d:h:m:s]: 02:216:09:57:39
Block: 604407 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 676264 RingCT/type: yes/0
Extra: 01d2bb8c889f31da0e7a3a855e9b63ce8af9c5499205e5905dd5d938557f987ed502110000000275e3f0e9000000000000000000

1 output(s) for total of 6.100265837000 dcy

stealth address amount amount idx
00: 4d630be8a9a12a58b2f506226b2566069c14802841852e45f9c183a4387d46ff 6.100265837000 1040744 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": 604417, "vin": [ { "gen": { "height": 604407 } } ], "vout": [ { "amount": 6100265837, "target": { "key": "4d630be8a9a12a58b2f506226b2566069c14802841852e45f9c183a4387d46ff" } } ], "extra": [ 1, 210, 187, 140, 136, 159, 49, 218, 14, 122, 58, 133, 94, 155, 99, 206, 138, 249, 197, 73, 146, 5, 229, 144, 93, 213, 217, 56, 85, 127, 152, 126, 213, 2, 17, 0, 0, 0, 2, 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