Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9f819374d8e01cdd048a6a11674b556b4c227ee3f601ae9fe71e5d53f22a4e6c

Tx prefix hash: 546317e6a44f48fae3812e30c64e28c189b68d485156615546542551a7a2d432
Tx public key: 2d13f546aa99cc8e9fb2019aa28bb26afa8ab76e8c7311dea8c1e8bda7014565
Timestamp: 1734622206 Timestamp [UCT]: 2024-12-19 15:30:06 Age [y:d:h:m:s]: 00:020:10:58:18
Block: 1178696 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 14605 RingCT/type: yes/0
Extra: 012d13f546aa99cc8e9fb2019aa28bb26afa8ab76e8c7311dea8c1e8bda70145650211000000051f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: be66eb90ef5e12298c020a6c3109e4ffe2f4a739ec372909a4f4a31c0c7981ad 0.600000000000 1665085 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": 1178706, "vin": [ { "gen": { "height": 1178696 } } ], "vout": [ { "amount": 600000000, "target": { "key": "be66eb90ef5e12298c020a6c3109e4ffe2f4a739ec372909a4f4a31c0c7981ad" } } ], "extra": [ 1, 45, 19, 245, 70, 170, 153, 204, 142, 159, 178, 1, 154, 162, 139, 178, 106, 250, 138, 183, 110, 140, 115, 17, 222, 168, 193, 232, 189, 167, 1, 69, 101, 2, 17, 0, 0, 0, 5, 31, 10, 83, 235, 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