Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 464a1848da3e0a5cbb38c8397b8993cecd0f3bd92a017906351800979d22d763

Tx prefix hash: 30accbe633a0e9fa333c42e15cda91ab691d99dd3d4bf039a1f363438046d943
Tx public key: 46fba363d1d87589af6663c4b9a25a87a11c48e873ed0e8cf93576c55b575b2b
Timestamp: 1731092421 Timestamp [UCT]: 2024-11-08 19:00:21 Age [y:d:h:m:s]: 00:146:00:01:36
Block: 1149436 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 104161 RingCT/type: yes/0
Extra: 0146fba363d1d87589af6663c4b9a25a87a11c48e873ed0e8cf93576c55b575b2b021100000001007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f93fdd86f774bb5bf21fb63f4cd306d0173c0f4e583bcf73d4937ac2548437f3 0.600000000000 1634511 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": 1149446, "vin": [ { "gen": { "height": 1149436 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f93fdd86f774bb5bf21fb63f4cd306d0173c0f4e583bcf73d4937ac2548437f3" } } ], "extra": [ 1, 70, 251, 163, 99, 209, 216, 117, 137, 175, 102, 99, 196, 185, 162, 90, 135, 161, 28, 72, 232, 115, 237, 14, 140, 249, 53, 118, 197, 91, 87, 91, 43, 2, 17, 0, 0, 0, 1, 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