Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cf47c473a652e877167833862de14fb2f146d17aaeef2e29691c4f2212a94ce1

Tx prefix hash: ebd438ac2f9cde8c301fdab374f5ea472ac0dd930c3f129f0fbb00a1ea487ad5
Tx public key: 523bafdaf8f26dc882942b57f136b2510ee0ce43a3618522c9a5d8853e14ad17
Timestamp: 1728880499 Timestamp [UCT]: 2024-10-14 04:34:59 Age [y:d:h:m:s]: 00:170:17:44:29
Block: 1131182 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 121796 RingCT/type: yes/0
Extra: 01523bafdaf8f26dc882942b57f136b2510ee0ce43a3618522c9a5d8853e14ad1702110000000491e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 583f9d6e278634eb6d362e3c754a4fcd6754e39e4fdbd6a4f9615fef9902cde3 0.600000000000 1614063 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": 1131192, "vin": [ { "gen": { "height": 1131182 } } ], "vout": [ { "amount": 600000000, "target": { "key": "583f9d6e278634eb6d362e3c754a4fcd6754e39e4fdbd6a4f9615fef9902cde3" } } ], "extra": [ 1, 82, 59, 175, 218, 248, 242, 109, 200, 130, 148, 43, 87, 241, 54, 178, 81, 14, 224, 206, 67, 163, 97, 133, 34, 201, 165, 216, 133, 62, 20, 173, 23, 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