Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1b7104d94898e78ee2f494214766f6fac596bd6fb731f13aec458b60a733be7d

Tx prefix hash: 7a5e4ad13e8e84a32b74bcf78d8dfcc2f0ef2ead2e6b71ccd29fa11a49983f30
Tx public key: 4bf60581390177e0fcca9261cafb06480c568703a031ccd0ccc9e7c66f8d40e3
Timestamp: 1740476743 Timestamp [UCT]: 2025-02-25 09:45:43 Age [y:d:h:m:s]: 00:265:10:34:34
Block: 1226847 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 187478 RingCT/type: yes/0
Extra: 014bf60581390177e0fcca9261cafb06480c568703a031ccd0ccc9e7c66f8d40e30211000000028368266d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 34c2ab04489aaae6151495ddc6e927349ce44a4499b1d5c07f9e249821f106e1 0.600000000000 1713720 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": 1226857, "vin": [ { "gen": { "height": 1226847 } } ], "vout": [ { "amount": 600000000, "target": { "key": "34c2ab04489aaae6151495ddc6e927349ce44a4499b1d5c07f9e249821f106e1" } } ], "extra": [ 1, 75, 246, 5, 129, 57, 1, 119, 224, 252, 202, 146, 97, 202, 251, 6, 72, 12, 86, 135, 3, 160, 49, 204, 208, 204, 201, 231, 198, 111, 141, 64, 227, 2, 17, 0, 0, 0, 2, 131, 104, 38, 109, 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