Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3c1efc7d242c8c013427cccc2e4664a11e02630ecdb1dfb4c74717a17b8b1b5b

Tx prefix hash: 6886c132023233d50859ebbe709c65c823546f4c5c5be069776ce5283a9851e6
Tx public key: 2f4cdb49fd362d2ddce195c5383f344aa6151a5800b8f77179e59c5cacf13481
Timestamp: 1739234376 Timestamp [UCT]: 2025-02-11 00:39:36 Age [y:d:h:m:s]: 00:330:11:26:08
Block: 1216579 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 234027 RingCT/type: yes/0
Extra: 012f4cdb49fd362d2ddce195c5383f344aa6151a5800b8f77179e59c5cacf13481021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0f1561110b1fe69182ca2c328cd93f5c68b7b3c5911ac812dba1dd7665cf534d 0.600000000000 1703386 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": 1216589, "vin": [ { "gen": { "height": 1216579 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0f1561110b1fe69182ca2c328cd93f5c68b7b3c5911ac812dba1dd7665cf534d" } } ], "extra": [ 1, 47, 76, 219, 73, 253, 54, 45, 45, 220, 225, 149, 197, 56, 63, 52, 74, 166, 21, 26, 88, 0, 184, 247, 113, 121, 229, 156, 92, 172, 241, 52, 129, 2, 17, 0, 0, 0, 3, 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