Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2fcd15f57c443b3b1d4bf56a89f41ae3eb65257aaa5890dc9909253fa4016c83

Tx prefix hash: 4b60456b1748b29b91d718cd3106f804e166d8d36dd2881df3662240c208eaba
Tx public key: 45480432622e36bee2c6f4fb22bd22793397a30fab418a8de9a1bd06d8ad0e13
Timestamp: 1706549013 Timestamp [UCT]: 2024-01-29 17:23:33 Age [y:d:h:m:s]: 01:103:11:48:15
Block: 946019 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 335065 RingCT/type: yes/0
Extra: 0145480432622e36bee2c6f4fb22bd22793397a30fab418a8de9a1bd06d8ad0e1302110000000759dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 41e7f1980f4f6c5af258740f062ddc08387c973a3e53dcb4f94fc09aa557ab4d 0.600000000000 1404349 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": 946029, "vin": [ { "gen": { "height": 946019 } } ], "vout": [ { "amount": 600000000, "target": { "key": "41e7f1980f4f6c5af258740f062ddc08387c973a3e53dcb4f94fc09aa557ab4d" } } ], "extra": [ 1, 69, 72, 4, 50, 98, 46, 54, 190, 226, 198, 244, 251, 34, 189, 34, 121, 51, 151, 163, 15, 171, 65, 138, 141, 233, 161, 189, 6, 216, 173, 14, 19, 2, 17, 0, 0, 0, 7, 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