Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 337738a13bffc8f026c96be44fd205bfdc301bb00a959aedee429b80eefb5b11

Tx prefix hash: b739a4896d63f326959a42f945d4f824bb53db748144e70eb0eb687f27602929
Tx public key: dcee6044b6111a42ad2d0f83b73812c460385f39f93ef0cef3eb9b2dc5c85d60
Timestamp: 1736166001 Timestamp [UCT]: 2025-01-06 12:20:01 Age [y:d:h:m:s]: 00:162:02:41:40
Block: 1191453 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 115574 RingCT/type: yes/0
Extra: 01dcee6044b6111a42ad2d0f83b73812c460385f39f93ef0cef3eb9b2dc5c85d60021100000008007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bb61d4f48190884bd0514231efb30f2fbd52e887289a8f06a2acb913c6e98b3e 0.600000000000 1677992 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": 1191463, "vin": [ { "gen": { "height": 1191453 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bb61d4f48190884bd0514231efb30f2fbd52e887289a8f06a2acb913c6e98b3e" } } ], "extra": [ 1, 220, 238, 96, 68, 182, 17, 26, 66, 173, 45, 15, 131, 183, 56, 18, 196, 96, 56, 95, 57, 249, 62, 240, 206, 243, 235, 155, 45, 197, 200, 93, 96, 2, 17, 0, 0, 0, 8, 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