Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9f8513620f6287af55f1f91cd15a52e4878012d6eeefc0b9ef663d2f28c56c3a

Tx prefix hash: e01affe508f1d7262f324eb5f95494fcb5d6a14bebe2bf709064b18fc9b63fa4
Tx public key: 3b0874eff0ed5072359433b3d1a5a9587318e76dac77251b7bc32625301ab372
Timestamp: 1737386608 Timestamp [UCT]: 2025-01-20 15:23:28 Age [y:d:h:m:s]: 00:150:04:53:18
Block: 1201503 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 107078 RingCT/type: yes/0
Extra: 013b0874eff0ed5072359433b3d1a5a9587318e76dac77251b7bc32625301ab372021100000005007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5fb67cf5089f4b6c86fd6e6b6c2888bef14db3d04ea3f6a1b0d5abf545a52176 0.600000000000 1688156 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": 1201513, "vin": [ { "gen": { "height": 1201503 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5fb67cf5089f4b6c86fd6e6b6c2888bef14db3d04ea3f6a1b0d5abf545a52176" } } ], "extra": [ 1, 59, 8, 116, 239, 240, 237, 80, 114, 53, 148, 51, 179, 209, 165, 169, 88, 115, 24, 231, 109, 172, 119, 37, 27, 123, 195, 38, 37, 48, 26, 179, 114, 2, 17, 0, 0, 0, 5, 0, 127, 151, 138, 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