Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: feb7c737f3c71e3bd8177d30d1aed71f0c6e1330449c025eab084e45fafe87ea

Tx prefix hash: 8277dd3a8a57e4c59889565f96a5f741ad1fc92e47d5b74469a94dd773ea97ff
Tx public key: 7269b3cfa3ce79b8579af2cd4e0152367a702f544c6a56a1bb4de9f34ecf7b85
Timestamp: 1723430574 Timestamp [UCT]: 2024-08-12 02:42:54 Age [y:d:h:m:s]: 00:164:19:45:11
Block: 1085995 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 117865 RingCT/type: yes/0
Extra: 017269b3cfa3ce79b8579af2cd4e0152367a702f544c6a56a1bb4de9f34ecf7b8502110000000691e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 700753cea122b15c6d924e6ad61e21eab0cc0cb1df67949bf3a5dabd134417eb 0.600000000000 1560586 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": 1086005, "vin": [ { "gen": { "height": 1085995 } } ], "vout": [ { "amount": 600000000, "target": { "key": "700753cea122b15c6d924e6ad61e21eab0cc0cb1df67949bf3a5dabd134417eb" } } ], "extra": [ 1, 114, 105, 179, 207, 163, 206, 121, 184, 87, 154, 242, 205, 78, 1, 82, 54, 122, 112, 47, 84, 76, 106, 86, 161, 187, 77, 233, 243, 78, 207, 123, 133, 2, 17, 0, 0, 0, 6, 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