Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cf0287e603e6c76b9c362970d7d68806f4f9ffaef11bc5bdaba111cc5c18466b

Tx prefix hash: 9fe13e75320c76230ed3c6d8ed91867d7367fc6456142c49b821b8d18a1078eb
Tx public key: 0fc9a1cf7b0816fab48a3af69781855edcc5dd0f04268b347a6c8d34def28f2e
Timestamp: 1625647822 Timestamp [UCT]: 2021-07-07 08:50:22 Age [y:d:h:m:s]: 03:142:11:45:54
Block: 289604 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 872035 RingCT/type: yes/0
Extra: 010fc9a1cf7b0816fab48a3af69781855edcc5dd0f04268b347a6c8d34def28f2e0211000000774b22f71d000000000000000000

1 output(s) for total of 67.365466139000 dcy

stealth address amount amount idx
00: b5f64ce2fb8ef31749c91d405dfa6064276524420ada0842ece9997bf769a2e5 67.365466139000 606576 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": 289614, "vin": [ { "gen": { "height": 289604 } } ], "vout": [ { "amount": 67365466139, "target": { "key": "b5f64ce2fb8ef31749c91d405dfa6064276524420ada0842ece9997bf769a2e5" } } ], "extra": [ 1, 15, 201, 161, 207, 123, 8, 22, 250, 180, 138, 58, 246, 151, 129, 133, 94, 220, 197, 221, 15, 4, 38, 139, 52, 122, 108, 141, 52, 222, 242, 143, 46, 2, 17, 0, 0, 0, 119, 75, 34, 247, 29, 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