Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 07fdc53a4d07c73f816eb8c6628c63aaef5f7cdde8f4221ca22aa111d130e7d3

Tx prefix hash: 6a9512473f0558f410eda00e0346621ed539794f6b843ebd11e23eae2508ee35
Tx public key: 38de88d3965f93e5d210f396849d992239151c41d6647928e79c52917159319e
Timestamp: 1695619444 Timestamp [UCT]: 2023-09-25 05:24:04 Age [y:d:h:m:s]: 02:049:13:42:01
Block: 855630 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 555079 RingCT/type: yes/0
Extra: 0138de88d3965f93e5d210f396849d992239151c41d6647928e79c52917159319e021100000001faf35c9c000000000000000000

1 output(s) for total of 0.897310334000 dcy

stealth address amount amount idx
00: 514e1615e656d21d0b4f460b73df1f3e9d4af0931efcb8b62ff8845bcf9bfb59 0.897310334000 1309662 of 0

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": 855640, "vin": [ { "gen": { "height": 855630 } } ], "vout": [ { "amount": 897310334, "target": { "key": "514e1615e656d21d0b4f460b73df1f3e9d4af0931efcb8b62ff8845bcf9bfb59" } } ], "extra": [ 1, 56, 222, 136, 211, 150, 95, 147, 229, 210, 16, 243, 150, 132, 157, 153, 34, 57, 21, 28, 65, 214, 100, 121, 40, 231, 156, 82, 145, 113, 89, 49, 158, 2, 17, 0, 0, 0, 1, 250, 243, 92, 156, 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