Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0063cef7b7ae933ecfc6ee0c1acfaa9c76957cef3f8040654a3ec90fae1253ab

Tx prefix hash: 661315e1a9df1d3a0f6cd6e9d4841005b22a553b4f4c986033fd000023bd68c7
Tx public key: a9fb54cc9802a2b6ebab5a2c5eeeb3c449c66ff82415891f5eb161e26cbe723f
Timestamp: 1696805501 Timestamp [UCT]: 2023-10-08 22:51:41 Age [y:d:h:m:s]: 01:257:14:18:02
Block: 865470 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 444982 RingCT/type: yes/0
Extra: 01a9fb54cc9802a2b6ebab5a2c5eeeb3c449c66ff82415891f5eb161e26cbe723f021100000001faf35c9c000000000000000000

1 output(s) for total of 0.832412609000 dcy

stealth address amount amount idx
00: 4bc2b6a4b95ca1831cdb26a030a8087a2c5a2a853a2e81b8ebdd2727a3525b27 0.832412609000 1320006 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": 865480, "vin": [ { "gen": { "height": 865470 } } ], "vout": [ { "amount": 832412609, "target": { "key": "4bc2b6a4b95ca1831cdb26a030a8087a2c5a2a853a2e81b8ebdd2727a3525b27" } } ], "extra": [ 1, 169, 251, 84, 204, 152, 2, 162, 182, 235, 171, 90, 44, 94, 238, 179, 196, 73, 198, 111, 248, 36, 21, 137, 31, 94, 177, 97, 226, 108, 190, 114, 63, 2, 17, 0, 0, 0, 1, 250, 243, 92, 156, 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