Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 972e73b4514c3803b1e8940ca95e8d8ef82e77747664a3b075deabd971903906

Tx prefix hash: 14c67a0ba58625739f3669a9fa074844aebea4ba50de001f5c9f93dea7c839a2
Tx public key: aae2873629541d1fbb4d09b3875d378a57f589713fec2bca7ac6aae7d68f91fd
Timestamp: 1704663685 Timestamp [UCT]: 2024-01-07 21:41:25 Age [y:d:h:m:s]: 01:008:17:12:07
Block: 930388 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 267563 RingCT/type: yes/0
Extra: 01aae2873629541d1fbb4d09b3875d378a57f589713fec2bca7ac6aae7d68f91fd02110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3097994f3aca7dc25404de37dde33910c175c0f3c21236a474512a5f947310e7 0.600000000000 1388270 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": 930398, "vin": [ { "gen": { "height": 930388 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3097994f3aca7dc25404de37dde33910c175c0f3c21236a474512a5f947310e7" } } ], "extra": [ 1, 170, 226, 135, 54, 41, 84, 29, 31, 187, 77, 9, 179, 135, 93, 55, 138, 87, 245, 137, 113, 63, 236, 43, 202, 122, 198, 170, 231, 214, 143, 145, 253, 2, 17, 0, 0, 0, 1, 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