Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 617d7b1f2955c8ba4555f95c379395849d29213eca0043534ea8464fc4d0761c

Tx prefix hash: 7fe391ca5527fc47d531958c291d438bf3becfe44a19b8d1e55c246a8ab23203
Tx public key: c24bbff81c2bc4f2a90e4ab3e4da9cbbd3bca375684d51d9771dc5ad4b837c1b
Timestamp: 1702275995 Timestamp [UCT]: 2023-12-11 06:26:35 Age [y:d:h:m:s]: 01:118:12:46:15
Block: 910609 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 345850 RingCT/type: yes/0
Extra: 01c24bbff81c2bc4f2a90e4ab3e4da9cbbd3bca375684d51d9771dc5ad4b837c1b021100000007faf35c9c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d2f7f6291ea04466c25171eb98c78b98aebfe748f355e347f6e1fd9d031984c5 0.600000000000 1367770 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": 910619, "vin": [ { "gen": { "height": 910609 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d2f7f6291ea04466c25171eb98c78b98aebfe748f355e347f6e1fd9d031984c5" } } ], "extra": [ 1, 194, 75, 191, 248, 28, 43, 196, 242, 169, 14, 74, 179, 228, 218, 156, 187, 211, 188, 163, 117, 104, 77, 81, 217, 119, 29, 197, 173, 75, 131, 124, 27, 2, 17, 0, 0, 0, 7, 250, 243, 92, 156, 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