Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 072fab5e4a4c1f08f17e3a15b7f76fea7652a251bc09a221591b85f7ab4e45eb

Tx prefix hash: c9948462710b8669cee4ac7a8299e39edf468078e1c253e0bc8a5f04ca9ab96a
Tx public key: b5c45435a0eb1f97f09d12788083ac885b472f6aab4849cdaeb07805484da3e4
Timestamp: 1646520423 Timestamp [UCT]: 2022-03-05 22:47:03 Age [y:d:h:m:s]: 02:207:18:31:55
Block: 452134 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 667972 RingCT/type: yes/0
Extra: 01b5c45435a0eb1f97f09d12788083ac885b472f6aab4849cdaeb07805484da3e402110000000406faf294000000000000000000

1 output(s) for total of 19.493626644000 dcy

stealth address amount amount idx
00: 00e5791f2d3ce617c8a3e9c9c855dd8057fe7c715e64e6da494fcca4d3ed7afa 19.493626644000 867379 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": 452144, "vin": [ { "gen": { "height": 452134 } } ], "vout": [ { "amount": 19493626644, "target": { "key": "00e5791f2d3ce617c8a3e9c9c855dd8057fe7c715e64e6da494fcca4d3ed7afa" } } ], "extra": [ 1, 181, 196, 84, 53, 160, 235, 31, 151, 240, 157, 18, 120, 128, 131, 172, 136, 91, 71, 47, 106, 171, 72, 73, 205, 174, 176, 120, 5, 72, 77, 163, 228, 2, 17, 0, 0, 0, 4, 6, 250, 242, 148, 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