Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d0f7ae0e3e135ac6e57a8448c4a74a5d11fb171a41137fe46fb6e3ab8093c12d

Tx prefix hash: 7005331d33cd80ae7c07a544adc0373eee89a6782d97740312d0c2b231865be9
Tx public key: f1ed6ebd8350e9f3664e5732809006bac68b100aef1a67ebb6bb22b32a20b6bf
Timestamp: 1737470540 Timestamp [UCT]: 2025-01-21 14:42:20 Age [y:d:h:m:s]: 00:147:07:30:04
Block: 1202209 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 105024 RingCT/type: yes/0
Extra: 01f1ed6ebd8350e9f3664e5732809006bac68b100aef1a67ebb6bb22b32a20b6bf0211000000041f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bf87fd5fd5b21ae775e75a9f9663bdb6dadd23efc3c321f2eb35ff894a738245 0.600000000000 1688872 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": 1202219, "vin": [ { "gen": { "height": 1202209 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bf87fd5fd5b21ae775e75a9f9663bdb6dadd23efc3c321f2eb35ff894a738245" } } ], "extra": [ 1, 241, 237, 110, 189, 131, 80, 233, 243, 102, 78, 87, 50, 128, 144, 6, 186, 198, 139, 16, 10, 239, 26, 103, 235, 182, 187, 34, 179, 42, 32, 182, 191, 2, 17, 0, 0, 0, 4, 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