Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0acd937726c252dd09331818c856512c1770faa3936aac8b4d651b8fd9c00aa0

Tx prefix hash: b636189c0fbb2d33f5284b7bba6c6ab167df4a52ff6d37bdec1bbf5e7cdf40e8
Tx public key: f4e91ca222cc464f1ae0f1739e1e9e09163cc1dfa85ac8bc07fc812272165e7c
Timestamp: 1713259566 Timestamp [UCT]: 2024-04-16 09:26:06 Age [y:d:h:m:s]: 00:338:20:59:37
Block: 1001659 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 242283 RingCT/type: yes/0
Extra: 01f4e91ca222cc464f1ae0f1739e1e9e09163cc1dfa85ac8bc07fc812272165e7c0211000000040011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fc6fc111b77d040ded284f4aff99d52840017243275deec0cb1ea0f14a7f5da2 0.600000000000 1462167 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": 1001669, "vin": [ { "gen": { "height": 1001659 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fc6fc111b77d040ded284f4aff99d52840017243275deec0cb1ea0f14a7f5da2" } } ], "extra": [ 1, 244, 233, 28, 162, 34, 204, 70, 79, 26, 224, 241, 115, 158, 30, 158, 9, 22, 60, 193, 223, 168, 90, 200, 188, 7, 252, 129, 34, 114, 22, 94, 124, 2, 17, 0, 0, 0, 4, 0, 17, 5, 91, 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