Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3eb2db131407447245121137c64abc1a13f731063dd524bccdafbdfce744b8b9

Tx prefix hash: 4871f48321353dfa25a81d99e26674646761dadd125fcddd6db7dc548479afb5
Tx public key: cdcbe346f25986e1c6f364f20142fd63f4f8c97fc8d1619799a4f79e61711709
Timestamp: 1725651321 Timestamp [UCT]: 2024-09-06 19:35:21 Age [y:d:h:m:s]: 00:229:15:53:21
Block: 1104410 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 163997 RingCT/type: yes/0
Extra: 01cdcbe346f25986e1c6f364f20142fd63f4f8c97fc8d1619799a4f79e6171170902110000000491e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 73647c9430e3d0f9fd6c68f081e0f36bb0a70943a6b7d5ef8d6dc4d793eae7b9 0.600000000000 1581539 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": 1104420, "vin": [ { "gen": { "height": 1104410 } } ], "vout": [ { "amount": 600000000, "target": { "key": "73647c9430e3d0f9fd6c68f081e0f36bb0a70943a6b7d5ef8d6dc4d793eae7b9" } } ], "extra": [ 1, 205, 203, 227, 70, 242, 89, 134, 225, 198, 243, 100, 242, 1, 66, 253, 99, 244, 248, 201, 127, 200, 209, 97, 151, 153, 164, 247, 158, 97, 113, 23, 9, 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