Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fa6e41afaa72a13f3f1184318b9a70160d48cea967c78ea803a85f6fcb9a0804

Tx prefix hash: b9a524b7782c2f4190daf42a76087b2ead949b79277b21f98749a2a31d117e12
Tx public key: 4dfb1d0f29ec802dcf6932e5eea9d1457886fcd79755cbead0ee32a7ec8374e5
Timestamp: 1729100300 Timestamp [UCT]: 2024-10-16 17:38:20 Age [y:d:h:m:s]: 00:148:21:57:30
Block: 1132994 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 106220 RingCT/type: yes/0
Extra: 014dfb1d0f29ec802dcf6932e5eea9d1457886fcd79755cbead0ee32a7ec8374e502110000000491e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 28122e7fcd3d893f0ca08c20a30cc9f1c08bfa92957c71f27cbc2aad57159798 0.600000000000 1616055 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": 1133004, "vin": [ { "gen": { "height": 1132994 } } ], "vout": [ { "amount": 600000000, "target": { "key": "28122e7fcd3d893f0ca08c20a30cc9f1c08bfa92957c71f27cbc2aad57159798" } } ], "extra": [ 1, 77, 251, 29, 15, 41, 236, 128, 45, 207, 105, 50, 229, 238, 169, 209, 69, 120, 134, 252, 215, 151, 85, 203, 234, 208, 238, 50, 167, 236, 131, 116, 229, 2, 17, 0, 0, 0, 4, 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