Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a35955e4e0a480ab9e9e9a49cbf584136f54d6fc17c91a1196f045a11d832a41

Tx prefix hash: 716f790a1e2d2dae619fe529d5e9f99f67b161f9ec9920db1bf1f9a6c0a8e52e
Tx public key: 012d7a0251869fb720048cfcae6ccb6b5c4deaa55ddf0c7ee99029e6942a5da8
Timestamp: 1713654738 Timestamp [UCT]: 2024-04-20 23:12:18 Age [y:d:h:m:s]: 00:351:02:16:53
Block: 1004937 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 250993 RingCT/type: yes/0
Extra: 01012d7a0251869fb720048cfcae6ccb6b5c4deaa55ddf0c7ee99029e6942a5da80211000000030011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b7ca2109e5419397e09d2f94bffc74395f59c592b3e4b7e985d9644b226ba2d4 0.600000000000 1465511 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": 1004947, "vin": [ { "gen": { "height": 1004937 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b7ca2109e5419397e09d2f94bffc74395f59c592b3e4b7e985d9644b226ba2d4" } } ], "extra": [ 1, 1, 45, 122, 2, 81, 134, 159, 183, 32, 4, 140, 252, 174, 108, 203, 107, 92, 77, 234, 165, 93, 223, 12, 126, 233, 144, 41, 230, 148, 42, 93, 168, 2, 17, 0, 0, 0, 3, 0, 17, 5, 91, 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