Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fc84adc3a53e4556e14197e118d0449606a3a523cb336cdce69d675c819de3f1

Tx prefix hash: 14b3e5559dc1e41666116b3991046c427b308d0920d67e2d7f97dd13cd4f98b8
Tx public key: 587581f5334ed579aa365a6fdc159434d686c45e33e19a2a6e341fdba1bc0302
Timestamp: 1696563107 Timestamp [UCT]: 2023-10-06 03:31:47 Age [y:d:h:m:s]: 01:187:06:24:40
Block: 863446 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 394894 RingCT/type: yes/0
Extra: 01587581f5334ed579aa365a6fdc159434d686c45e33e19a2a6e341fdba1bc0302021100000001faf35c9c000000000000000000

1 output(s) for total of 0.845366445000 dcy

stealth address amount amount idx
00: 228703c3242bb564395e8c1c81ad0a3d459b5b19b9411f1116286df370326bcc 0.845366445000 1317902 of 0

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": 863456, "vin": [ { "gen": { "height": 863446 } } ], "vout": [ { "amount": 845366445, "target": { "key": "228703c3242bb564395e8c1c81ad0a3d459b5b19b9411f1116286df370326bcc" } } ], "extra": [ 1, 88, 117, 129, 245, 51, 78, 213, 121, 170, 54, 90, 111, 220, 21, 148, 52, 214, 134, 196, 94, 51, 225, 154, 42, 110, 52, 31, 219, 161, 188, 3, 2, 2, 17, 0, 0, 0, 1, 250, 243, 92, 156, 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