Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1bbf2fc0a3401cb0d21b04dc1974363a7f47e2ebf5494975c8e681c773a9c052

Tx prefix hash: f82cbee5b91edfbf146a15426837a5e824417939a82d67a7820a69ceea36d0ac
Tx public key: 2cf8d252cf62d772454db5f51c0a2e51bf290ce5f68a453d8b9c330c67be22fc
Timestamp: 1717564007 Timestamp [UCT]: 2024-06-05 05:06:47 Age [y:d:h:m:s]: 00:308:15:12:21
Block: 1037370 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 220554 RingCT/type: yes/0
Extra: 012cf8d252cf62d772454db5f51c0a2e51bf290ce5f68a453d8b9c330c67be22fc02110000000959dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 694e0abb7f22cf5c335c829944fbf71ca5472e0326351c6b049d0c6daf2905f2 0.600000000000 1505901 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": 1037380, "vin": [ { "gen": { "height": 1037370 } } ], "vout": [ { "amount": 600000000, "target": { "key": "694e0abb7f22cf5c335c829944fbf71ca5472e0326351c6b049d0c6daf2905f2" } } ], "extra": [ 1, 44, 248, 210, 82, 207, 98, 215, 114, 69, 77, 181, 245, 28, 10, 46, 81, 191, 41, 12, 229, 246, 138, 69, 61, 139, 156, 51, 12, 103, 190, 34, 252, 2, 17, 0, 0, 0, 9, 89, 218, 211, 245, 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