Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 52b6390d4ebc7062d37b55e2f87049aeffcb451bd43475f034bda0110ddfe065

Tx prefix hash: a546e0e85d6ae536827189d72198609c217bc03fcb1524ab57fc8d6853b7e893
Tx public key: c143171dbd864d89e9c8cdee349a5a736365f87a49af2d7e38945d0f27a3c98a
Timestamp: 1702677429 Timestamp [UCT]: 2023-12-15 21:57:09 Age [y:d:h:m:s]: 01:190:17:21:46
Block: 913936 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 397269 RingCT/type: yes/0
Extra: 01c143171dbd864d89e9c8cdee349a5a736365f87a49af2d7e38945d0f27a3c98a02110000000575e3f0e9000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bfb6101986fd61642ae6390654c3ee1a45f03e3f22b271f76d4b9ef7823eafc8 0.600000000000 1371216 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": 913946, "vin": [ { "gen": { "height": 913936 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bfb6101986fd61642ae6390654c3ee1a45f03e3f22b271f76d4b9ef7823eafc8" } } ], "extra": [ 1, 193, 67, 23, 29, 189, 134, 77, 137, 233, 200, 205, 238, 52, 154, 90, 115, 99, 101, 248, 122, 73, 175, 45, 126, 56, 148, 93, 15, 39, 163, 201, 138, 2, 17, 0, 0, 0, 5, 117, 227, 240, 233, 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