Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d37bee7de3cf86137e1685902fd054591d08df3fdf0181e054aef9466cd227f1

Tx prefix hash: fcb54d2933ca15a39d9cdf529655b166cded4fdbb698f056134193e115b491fd
Tx public key: da1a780f312960f344e74158f3bfb2a45cc724a7a46b069a63cabbbfdf474a27
Timestamp: 1726829274 Timestamp [UCT]: 2024-09-20 10:47:54 Age [y:d:h:m:s]: 00:065:06:59:26
Block: 1114175 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 46666 RingCT/type: yes/0
Extra: 01da1a780f312960f344e74158f3bfb2a45cc724a7a46b069a63cabbbfdf474a27021100000004685eb510000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6dc7a0047422aac31962b728c8e39a0ea3b98f03e3f3d6aa53ac996928e062f1 0.600000000000 1593974 of 15

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": 1114185, "vin": [ { "gen": { "height": 1114175 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6dc7a0047422aac31962b728c8e39a0ea3b98f03e3f3d6aa53ac996928e062f1" } } ], "extra": [ 1, 218, 26, 120, 15, 49, 41, 96, 243, 68, 231, 65, 88, 243, 191, 178, 164, 92, 199, 36, 167, 164, 107, 6, 154, 99, 202, 187, 191, 223, 71, 74, 39, 2, 17, 0, 0, 0, 4, 104, 94, 181, 16, 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