Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3df4d61661529b19566f6fc429c54415aa633c1237f7b770dfeda3077b1a8d86

Tx prefix hash: e9d287b206181a6d9224e58bf9670bc478fd85ee6394b1c79699d10410288438
Tx public key: 9dd3fc2ab09c0d24ae07297ae3d971e55bdaf43e653f7cdca76bd9dbe18b5ae0
Timestamp: 1737380796 Timestamp [UCT]: 2025-01-20 13:46:36 Age [y:d:h:m:s]: 00:148:22:43:23
Block: 1201452 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 106205 RingCT/type: yes/0
Extra: 019dd3fc2ab09c0d24ae07297ae3d971e55bdaf43e653f7cdca76bd9dbe18b5ae0021100000008007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bf11c4e9cd66c2bd8ae393400edc0f301e04639e12faf02731b6d6602ddce27b 0.600000000000 1688105 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": 1201462, "vin": [ { "gen": { "height": 1201452 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bf11c4e9cd66c2bd8ae393400edc0f301e04639e12faf02731b6d6602ddce27b" } } ], "extra": [ 1, 157, 211, 252, 42, 176, 156, 13, 36, 174, 7, 41, 122, 227, 217, 113, 229, 91, 218, 244, 62, 101, 63, 124, 220, 167, 107, 217, 219, 225, 139, 90, 224, 2, 17, 0, 0, 0, 8, 0, 127, 151, 138, 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