Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f5fd48b5b0e3f200284d71d0ded1fc2d5d0e431f1d091a2c3e0d9ce51d2c4173

Tx prefix hash: 2cccf4fc9da88b92a24491d13ffb2775a46e6dbf6745153dfcc79c707a88f9ac
Tx public key: 94ebeea410fa62ce9e0644c1994395d59517d71576eea179c5f1e380706fa6dc
Timestamp: 1726161700 Timestamp [UCT]: 2024-09-12 17:21:40 Age [y:d:h:m:s]: 00:101:01:34:56
Block: 1108632 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 72312 RingCT/type: yes/0
Extra: 0194ebeea410fa62ce9e0644c1994395d59517d71576eea179c5f1e380706fa6dc021100000005e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b5a273cdcacc2a7a58de4c56532dba163c26095f84186bed95d86525b81aa303 0.600000000000 1586599 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": 1108642, "vin": [ { "gen": { "height": 1108632 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b5a273cdcacc2a7a58de4c56532dba163c26095f84186bed95d86525b81aa303" } } ], "extra": [ 1, 148, 235, 238, 164, 16, 250, 98, 206, 158, 6, 68, 193, 153, 67, 149, 213, 149, 23, 215, 21, 118, 238, 161, 121, 197, 241, 227, 128, 112, 111, 166, 220, 2, 17, 0, 0, 0, 5, 233, 20, 221, 21, 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