Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f86c711d718dd9c2ff1392cf82f2e60fd2b57462465ec0f97a3689486fb90e89

Tx prefix hash: 94a9c76c0975eee71f3b2d69f0a46f5efd018625de537228a8b20614ef7d993d
Tx public key: f106bd333d94270b1f05cf6cd8bc1974aef3bf3497105f7d77c2f52a09f905d2
Timestamp: 1730911156 Timestamp [UCT]: 2024-11-06 16:39:16 Age [y:d:h:m:s]: 00:186:00:03:57
Block: 1147929 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 132788 RingCT/type: yes/0
Extra: 01f106bd333d94270b1f05cf6cd8bc1974aef3bf3497105f7d77c2f52a09f905d202110000000325a35a0f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e3e0a8e2128e5ebd71c3d7e4487928d6a4b852a15c397886205c0accfc91aee0 0.600000000000 1632644 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": 1147939, "vin": [ { "gen": { "height": 1147929 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e3e0a8e2128e5ebd71c3d7e4487928d6a4b852a15c397886205c0accfc91aee0" } } ], "extra": [ 1, 241, 6, 189, 51, 61, 148, 39, 11, 31, 5, 207, 108, 216, 188, 25, 116, 174, 243, 191, 52, 151, 16, 95, 125, 119, 194, 245, 42, 9, 249, 5, 210, 2, 17, 0, 0, 0, 3, 37, 163, 90, 15, 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