Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7bd70df77f4118c4133979aaac39e9397cd2f404f8398d53fc7e93505fd1c423

Tx prefix hash: b458c0a4101e26fd37c3b0cb78fbe6b183ab7966b45282849603df6029154a8d
Tx public key: 3973d1c1ea5f430204ee4a7e0fedef858945a73575dce7673f886e3c4afefaad
Timestamp: 1648218717 Timestamp [UCT]: 2022-03-25 14:31:57 Age [y:d:h:m:s]: 03:032:22:39:52
Block: 466140 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 803746 RingCT/type: yes/0
Extra: 013973d1c1ea5f430204ee4a7e0fedef858945a73575dce7673f886e3c4afefaad0211000000055eb576c5000000000000000000

1 output(s) for total of 17.518016506000 dcy

stealth address amount amount idx
00: e95d7c7faf82281a926996e02e892293abeedce118b760f80eb9892f94bb0043 17.518016506000 884385 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": 466150, "vin": [ { "gen": { "height": 466140 } } ], "vout": [ { "amount": 17518016506, "target": { "key": "e95d7c7faf82281a926996e02e892293abeedce118b760f80eb9892f94bb0043" } } ], "extra": [ 1, 57, 115, 209, 193, 234, 95, 67, 2, 4, 238, 74, 126, 15, 237, 239, 133, 137, 69, 167, 53, 117, 220, 231, 103, 63, 136, 110, 60, 74, 254, 250, 173, 2, 17, 0, 0, 0, 5, 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