Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b9f28828e66a15b3fa97b987bf89dedabfb9d475cef4192718875ee07c2f2064

Tx prefix hash: 9cf89335e984f7e3236bba992e9f2c22e84cf5482997c17e6bb9e1571b69e4b8
Tx public key: cf8d467017e45dfb8544d21734c2f85e7b8d7c1ec0a8642dfb23ef86f70824cb
Timestamp: 1681351445 Timestamp [UCT]: 2023-04-13 02:04:05 Age [y:d:h:m:s]: 01:273:13:33:27
Block: 737373 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 457030 RingCT/type: yes/0
Extra: 01cf8d467017e45dfb8544d21734c2f85e7b8d7c1ec0a8642dfb23ef86f70824cb021100000004b3164c24000000000000000000

1 output(s) for total of 2.211960537000 dcy

stealth address amount amount idx
00: b20e6d6b533c193832fd24a0a91496bae0d6f662de4d0157d65935b61b7e2855 2.211960537000 1183922 of 0

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": 737383, "vin": [ { "gen": { "height": 737373 } } ], "vout": [ { "amount": 2211960537, "target": { "key": "b20e6d6b533c193832fd24a0a91496bae0d6f662de4d0157d65935b61b7e2855" } } ], "extra": [ 1, 207, 141, 70, 112, 23, 228, 93, 251, 133, 68, 210, 23, 52, 194, 248, 94, 123, 141, 124, 30, 192, 168, 100, 45, 251, 35, 239, 134, 247, 8, 36, 203, 2, 17, 0, 0, 0, 4, 179, 22, 76, 36, 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