Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8264ed12922f85dee88e734dcdc7d1ca753a6008de81dc3e39e5b578bd95ac8a

Tx prefix hash: 23d21bd157c511bfd86efc1f5788164b194f4113f9dea42cbad6baf213e2e42e
Tx public key: fb5bb827a010aa6b6e10ef40d2bd8b252b2cfccfec4b6538e9bc925052311133
Timestamp: 1725047025 Timestamp [UCT]: 2024-08-30 19:43:45 Age [y:d:h:m:s]: 01:061:19:26:35
Block: 1099394 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 302609 RingCT/type: yes/0
Extra: 01fb5bb827a010aa6b6e10ef40d2bd8b252b2cfccfec4b6538e9bc92505231113302110000000191e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9eae4f99cab208c5bf834ea86ce5dd08b3ed762cac6850c51dab490c75b2f6d2 0.600000000000 1575355 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": 1099404, "vin": [ { "gen": { "height": 1099394 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9eae4f99cab208c5bf834ea86ce5dd08b3ed762cac6850c51dab490c75b2f6d2" } } ], "extra": [ 1, 251, 91, 184, 39, 160, 16, 170, 107, 110, 16, 239, 64, 210, 189, 139, 37, 43, 44, 252, 207, 236, 75, 101, 56, 233, 188, 146, 80, 82, 49, 17, 51, 2, 17, 0, 0, 0, 1, 145, 225, 60, 4, 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