Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 44c76be37cdbb6d7ce78e41a80d8d88075ac015d4c6eb4a9f46f3de1be8c50b8

Tx prefix hash: 661e7661e00d97870fc8995b6916a695f96f7a22a813e0fa64625a6ab13e836a
Tx public key: 7470ed817095ebbfb84f9702fce036dd1d030c3115883a15b6eaa9c551f503bc
Timestamp: 1718702392 Timestamp [UCT]: 2024-06-18 09:19:52 Age [y:d:h:m:s]: 00:363:14:07:59
Block: 1046804 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 259756 RingCT/type: yes/0
Extra: 017470ed817095ebbfb84f9702fce036dd1d030c3115883a15b6eaa9c551f503bc02110000000359dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a9427785489b0efb8434baf454e1f7f3250f2b15a919a2b0f83085b62c0bda84 0.600000000000 1516623 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": 1046814, "vin": [ { "gen": { "height": 1046804 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a9427785489b0efb8434baf454e1f7f3250f2b15a919a2b0f83085b62c0bda84" } } ], "extra": [ 1, 116, 112, 237, 129, 112, 149, 235, 191, 184, 79, 151, 2, 252, 224, 54, 221, 29, 3, 12, 49, 21, 136, 58, 21, 182, 234, 169, 197, 81, 245, 3, 188, 2, 17, 0, 0, 0, 3, 89, 218, 211, 245, 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