Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: eb5ed122949686f2634e34b871d6d33cc3094549c4c7d526e0638724c05d1b48

Tx prefix hash: d0161e002002d4df95d738aa30430a35dc0c6e78e947a53a08dd1a44c66d38e3
Tx public key: 0a45ea1a84e63a86a7a7a431cb1fe86358b84ef90c58b75a98ccc90f820ebda4
Timestamp: 1699442087 Timestamp [UCT]: 2023-11-08 11:14:47 Age [y:d:h:m:s]: 01:134:16:33:01
Block: 887126 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 357440 RingCT/type: yes/0
Extra: 010a45ea1a84e63a86a7a7a431cb1fe86358b84ef90c58b75a98ccc90f820ebda402110000000133af99f4000000000000000000

1 output(s) for total of 0.705640178000 dcy

stealth address amount amount idx
00: d3d477a8547bdea8a4d62714cff4c3c31da0b6fd038550ec9c2ce8223151ed53 0.705640178000 1342981 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": 887136, "vin": [ { "gen": { "height": 887126 } } ], "vout": [ { "amount": 705640178, "target": { "key": "d3d477a8547bdea8a4d62714cff4c3c31da0b6fd038550ec9c2ce8223151ed53" } } ], "extra": [ 1, 10, 69, 234, 26, 132, 230, 58, 134, 167, 167, 164, 49, 203, 31, 232, 99, 88, 184, 78, 249, 12, 88, 183, 90, 152, 204, 201, 15, 130, 14, 189, 164, 2, 17, 0, 0, 0, 1, 51, 175, 153, 244, 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