Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8c0574d6e5f0198382285e629292b20e2ce727166e1fc93e11156584954922d1

Tx prefix hash: 8befc4ed2bf851b2b8c9516dc030e5560526ab2957dcb7a67d1439b51665ba7d
Tx public key: 52335616e9ede0e4b4603ec4434594ba6de96ad0f65b6b33d4126b753376bb5c
Timestamp: 1576943687 Timestamp [UCT]: 2019-12-21 15:54:47 Age [y:d:h:m:s]: 05:008:12:51:07
Block: 29412 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1155362 RingCT/type: yes/0
Extra: 0152335616e9ede0e4b4603ec4434594ba6de96ad0f65b6b33d4126b753376bb5c02110000001d8a2ee0d9000000000000000000

1 output(s) for total of 490.404219907000 dcy

stealth address amount amount idx
00: edfccae06f8fd920a7def525cb148cb5740d548def79ecade77cee54c3b63c09 490.404219907000 48316 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": 29422, "vin": [ { "gen": { "height": 29412 } } ], "vout": [ { "amount": 490404219907, "target": { "key": "edfccae06f8fd920a7def525cb148cb5740d548def79ecade77cee54c3b63c09" } } ], "extra": [ 1, 82, 51, 86, 22, 233, 237, 224, 228, 180, 96, 62, 196, 67, 69, 148, 186, 109, 233, 106, 208, 246, 91, 107, 51, 212, 18, 107, 117, 51, 118, 187, 92, 2, 17, 0, 0, 0, 29, 138, 46, 224, 217, 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